Why I did it

Currently when we loaded HWSKU Arista-7060X6-16PE-384C-O128S2 on two moby devices and connect their Paladin ports back to back, we can't get link up. It may help if we can get these links up and run the tests.

Work item tracking

• Microsoft ADO (number only):

How I did it

Created a new FANOUT HWSKU containing special lanemap and polarity configs so that we can load Arista-7060X6-16PE-384C-O128S2 on one Moby and Arista-7060X6-16PE-384C-O128S2-FANOUT and get Paladin ports up when connecting them back to back with the following setup:

Moby1                                    Moby2
HWSKU: Arista-7060X6-16PE-384C-O128S2    HWSKU: Arista-7060X6-16PE-384C-O128S2-FANOUT
#17                 <->                  #18
#19                 <->                  #20
#21                 <->                  #22
#23                 <->                  #24

#18                 <->                  #17
#20                 <->                  #19
#22                 <->                  #21
#24                 <->                  #23

How to verify it

Verified that all the Paladin ports can link up with the above setup.

Which release branch to backport (provide reason below if selected)

• 201811
• 201911
• 202006
• 202012
• 202106
• 202111
• 202205
• 202211
• 202305
• msft-202412

Tested branch (Please provide the tested image version)

• msft-202412

Description for the changelog

Created Arista-7060X6-16PE-384C-O128S2-FANOUT based on Arista-7060X6-16PE-384C-O128S2 and only update lanemap and polarity settings in bcm config.

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)